Add testing for shard scoped foreign keys #15571
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds testing for shard-scoped foreign keys. While making these changes we realised that for shard-scoped foreign keys, the foreign key columns have to be part of the sharding key, which automatically fails all the updates on those columns! 😿
So, we can currently only support
DELETE RESTRICT
andDELETE CASCADE
style operations. This PR adds the infra for adding the tests for all the scenarios but skips all the ones that don't work for now. For the same reason, I haven't enabled fuzzer tests either for shard-scoped foreign keys because of the very limited number of queries that actually work.Here are the tests that work as intended -
Related Issue(s)
Checklist
Deployment Notes